Processing and/or transmitting 3D data associated with a 3D model of an interior environment

ABSTRACT

Systems and techniques for processing and/or transmitting three-dimensional (3D) data are presented. A partitioning component receives captured 3D data associated with a 3D model of an interior environment and partitions the captured 3D data into at least one data chunk associated with at least a first level of detail and a second level of detail. A data component stores 3D data including at least the first level of detail and the second level of detail for the at least one data chunk. An output component transmits a portion of data from the at least one data chunk that is associated with the first level of detail or the second level of detail to a remote client device based on information associated with the first level of detail and the second level of detail.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to each of,U.S. patent application Ser. No. 15/187,611, filed Jun. 20, 2016, andentitled “PROCESSING AND/OR TRANSMITTING 3D DATA,” which is acontinuation of U.S. patent application Ser. No. 14/213,531, filed Mar.14, 2014, and entitled “PROCESSING AND/OR TRANSMITTING 3D DATA.” Theentireties of the foregoing applications listed herein are herebyincorporated by reference.

TECHNICAL FIELD

This disclosure relates generally to three-dimensional (3D) modeling,and more specifically, to processing and/or transmitting 3D data.

BACKGROUND

Digital three-dimensional (3D) models can be generated based on scans ofarchitectural spaces (e.g., houses, construction sites, office spaces,etc). Often times, 3D models generated based on scans of architecturalspaces comprise large amounts of data (e.g., data points, polygons,textures, etc). As such, streaming 3D models to remote client devices(e.g., to display the 3D models on a remote client device) is often slowbecause of limited data bandwidth relative to the size of the 3D models.Moreover, once data for 3D models is delivered to a remote clientdevice, rendering the 3D model or parts of the 3D model for displayrequires additional time. Furthermore, once data for 3D models isdelivered to a remote client device, computing resources for renderingthe 3D model or parts of the 3D model (e.g., texture memory, number ofpolygons that can be rendered at a certain frame rate, etc.) can belimited. As such, user experience is often hindered and/or computingresources are often constrained when employing current techniques forstreaming 3D models to a remote client device. Accordingly, currenttechniques for streaming 3D models to a remote client device can beimproved.

SUMMARY

The following presents a simplified summary of the specification inorder to provide a basic understanding of some aspects of thespecification. This summary is not an extensive overview of thespecification. It is intended to neither identify key or criticalelements of the specification, nor delineate any scope of the particularimplementations of the specification or any scope of the claims. Itssole purpose is to present some concepts of the specification in asimplified form as a prelude to the more detailed description that ispresented later.

In accordance with an implementation, a system includes a partitioningcomponent, a data component, and an output component. The partitioningcomponent receives captured three-dimensional (3D) data associated witha 3D model of an interior environment and partitions the captured 3Ddata into at least one data chunk associated with at least a first levelof detail and a second level of detail. The data component stores 3Ddata including at least the first level of detail and the second levelof detail for the at least one data chunk. The output componenttransmits a portion of data from the at least one data chunk that isassociated with the first level of detail or the second level of detailto a remote client device based on information associated with the firstlevel of detail and the second level of detail. In an aspect, thepartitioning component partitions the captured 3D data into the at leastone data chunk based on identified architectural elements of the 3Dmodel.

Additionally, a non-limiting implementation provides for receivingcaptured three-dimensional (3D) data associated with a 3D model of anindoor environment, partitioning the captured 3D data into at least onedata segment associated with multiple levels of detail, storing 3D dataincluding the multiple levels of detail associated with the at least onedata segment in a data structure, and transmitting the multiple levelsof detail for the at least one data segment to a remote device based onan order determined as a function of geometry data or texture dataassociated with the multiple levels of detail.

In accordance with another implementation, a system includes a server.The server partitions three-dimensional (3D) data associated with a 3Dmodel of an interior environment into at least one data chunk associatedwith multiple levels of detail, stores the multiple levels of detailassociated with the at least one data chunk in a data structure, andtransmits the multiple levels of detail associated with the at least onedata chunk to a remote device based on a transmission order determinedas a function of data associated with the multiple levels of detail.

In accordance with yet another implementation, a system includes apartitioning component, a data component, and an output component. Thepartitioning component receives captured three-dimensional (3D) dataassociated with a 3D model of an interior environment and partitions thecaptured 3D data into a data chunk associated with a level of detail anda plurality of other data chunks associated with other levels of detail.The data component stores 3D data including at least the level of detailfor the data chunk and the other levels of detail for the plurality ofother data chunks. The output component initially transmits the datachunk to a remote device and subsequently transmits a portion of datafrom the plurality of other data chunks to the remote device based oninformation associated with the other levels of detail.

The following description and the annexed drawings set forth certainillustrative aspects of the specification. These aspects are indicative,however, of but a few of the various ways in which the principles of thespecification may be employed. Other advantages and novel features ofthe specification will become apparent from the following detaileddescription of the specification when considered in conjunction with thedrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Numerous aspects, implementations, objects and advantages of the presentinvention will be apparent upon consideration of the following detaileddescription, taken in conjunction with the accompanying drawings, inwhich like reference characters refer to like parts throughout, and inwhich:

FIG. 1 illustrates a high-level block diagram of an example processingcomponent for processing and/or transmitting three-dimensional (3D)data, in accordance with various aspects and implementations describedherein;

FIG. 2 illustrates a high-level block diagram of a system for processingand/or transmitting 3D data, in accordance with various aspects andimplementations described herein;

FIG. 3 illustrates a high-level block diagram of another system forprocessing and/or transmitting 3D data, in accordance with variousaspects and implementations described herein;

FIG. 4 illustrates a diagram of subsections associated with a 3D model,in accordance with various aspects and implementations described herein;

FIG. 5 depicts a flow diagram of an example method for processing and/ortransmitting 3D data, in accordance with various aspects andimplementations described herein;

FIG. 6 depicts a flow diagram of another example method for processingand/or transmitting 3D data, in accordance with various aspects andimplementations described herein;

FIG. 7 depicts a flow diagram of yet another example method forprocessing and/or transmitting 3D data, in accordance with variousaspects and implementations described herein;

FIG. 8 depicts a flow diagram of yet another example method forprocessing and/or transmitting 3D data, in accordance with variousaspects and implementations described herein;

FIG. 9 depicts a flow diagram of an example method for sending datachunks from a server to a remote client device based on view position,in accordance with various aspects and implementations described herein;

FIG. 10 is a schematic block diagram illustrating a suitable operatingenvironment; and

FIG. 11 is a schematic block diagram of a sample-computing environment.

DETAILED DESCRIPTION

Various aspects of this disclosure are now described with reference tothe drawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of one or more aspects. It should beunderstood, however, that certain aspects of this disclosure may bepracticed without these specific details, or with other methods,components, materials, etc. In other instances, well-known structuresand devices are shown in block diagram form to facilitate describing oneor more aspects.

Digital three-dimensional (3D) models can be generated based on scans ofarchitectural spaces (e.g., houses, construction sites, office spaces,etc). Oftentimes, 3D models generated based on scans of architecturalspaces comprise large amounts of data (e.g., data points, polygons,textures, etc). As such, streaming 3D models to remote client devices(e.g., to display the 3D models on a remote client device) is often slowbecause of limited data bandwidth relative to the size of the 3D models.Moreover, once data for 3D models is delivered to a remote clientdevice, rendering the 3D model or parts of the 3D model for displayrequires additional time. Furthermore, once data for 3D models isdelivered to a remote client device, resources for rendering the 3Dmodel or parts of the 3D model (e.g., texture memory, number of polygonsthat can be rendered at a certain frame rate, etc.) are limited. Assuch, user experience is often hindered and/or computing resources areoften constrained when employing current techniques for streaming 3Dmodels to a remote client device. Accordingly, current techniques forstreaming 3D models to a remote client device can be improved.

To that end, techniques for processing and/or transmitting 3D data(e.g., 3D-reconstructed data) are presented. For example, the 3D data(e.g., the 3D-reconstructed data) can be generated based on a 3Dreconstruction system that allows automatic and/or semi-automaticcreation of 3D models of real-world locations (e.g., houses, apartments,construction sites, office spaces, commercial spaces, other livingspaces, other working spaces, etc.). In one example, the 3Dreconstruction system can employ 2D image data and/or depth datacaptured from 3D sensors (e.g., laser scanners, structured lightsystems, time-of-flight systems, etc.) to generate the 3D data (e.g.,the 3D-reconstructed data). In an aspect, the 3D data (e.g., the3D-reconstructed data) can be divided (e.g., automatically divided) intoone or more data chunks. A data chunk can be a chunk of a 3D model or aparticular region of a 3D model. The one or more data chunks can bedetermined based on architectural elements (e.g., walls, floors, rooms,objects, etc.) associated with the 3D data. For example, architecturalelements associated with the 3D data can be identified (e.g.,automatically identified), segmented (e.g., automatically segmented)and/or associated with data chunks. Each data chunk can be associatedwith one or more levels of detail. For example, each data chunk can beassociated with one or more levels of detail for geometry and/or one ormore levels of detail for texture (e.g., visual texture). In anotheraspect, an order for transmitting the one or more data chunks and/or thelevels of detail associated with each data chunk can be determined(e.g., automatically determined). For example, an order for streamingthe one or more data chunks and/or the levels of detail associated witheach data chunk to a remote device (e.g., a remote client device) can bedetermined. As such, loading time for rendering 3D data (e.g., 3Dmodels) that is streamed to a remote device can be improved.Furthermore, user experience when employing a remote client device toview 3D data (e.g., to view 3D models via a 3D model viewer) can beimproved.

Referring initially to FIG. 1, there is illustrated a system 100 thatcan facilitate processing and/or transmitting 3D data (e.g.,3D-reconstructed data), according to an aspect of the subjectdisclosure. In one example, the system 100 can be implemented on or inconnection with at least one server associated with 3D data (e.g.,3D-reconstructed data). The system 100 can be employed by varioussystems, such as, but not limited to 3D modeling systems, 3Dreconstruction systems, server systems, cloud-based systems, and thelike.

Specifically, the system 100 can provide a processing component 102 witha partitioning feature (e.g., partitioning component 104), a datafeature (e.g., data component 105), a selection feature (e.g., selectioncomponent 106) and/or an output feature (e.g., output component 108)that can be utilized in, for example, a 3D modeling application (e.g., a3D reconstruction application). The partitioning feature can receivecaptured 3D data associated with a 3D model of an interior environment.For example, a 3D model can comprise a 3D mesh (e.g., a triangle mesh, aquad mesh, a parametric mesh, etc.), a point cloud, surface elements(e.g., surfels) and/or other data captured by employing one or more 3Dsensors. Furthermore, the partitioning feature can partition thecaptured 3D data into at least one data chunk associated with at least afirst level of detail and a second level of detail. The data feature canstore 3D data including at least the first level of detail and thesecond level of detail for the at least one data chunk. The outputfeature can transmit a portion of data from the at least one data chunkthat is associated with the first level of detail or the second level ofdetail to a remote client device based on information (e.g., metadata)associated with the first level of detail and the second level ofdetail. The selection feature can select the portion of data from the atleast one data chunk that is associated with the first level of detailor the second level of detail based on the information associated withthe first level of detail and the second level of detail. In anembodiment, the system 100 can include the selection feature (e.g., theselection feature can be implemented on a server). In anotherembodiment, the selection feature can be implemented separate from thesystem 100 (e.g., the selection feature can be implemented on the remoteclient device).

In particular, the system 100 can include processing component 102. InFIG. 1, the processing component 102 includes a partitioning component104, a data component 105, a selection component 106 and/or an outputcomponent 108. Aspects of the systems, apparatuses or processesexplained in this disclosure can constitute machine-executablecomponent(s) embodied within machine(s), e.g., embodied in one or morecomputer readable mediums (or media) associated with one or moremachines. Such component(s), when executed by the one or more machines,e.g., computer(s), computing device(s), virtual machine(s), etc. cancause the machine(s) to perform the operations described. System 100 caninclude memory 112 for storing computer executable components andinstructions. System 100 can further include a processor 110 tofacilitate operation of the instructions (e.g., computer executablecomponents and instructions) by system 100.

The processing component 102 (e.g., with the partitioning component 104)can receive captured 3D data (e.g., CAPTURED 3D DATA shown in FIG. 1).The captured 3D data can be captured 3D-reconstructed data. In oneexample, the captured 3D data can be raw 3D-reconstruced data. Inanother example, the captured 3D data can be processed and/or segmented3D-reconstructed data. In an aspect, the captured 3D data can begenerated (e.g., captured) via at least one 3D reconstruction system.For example, the at least one 3D reconstruction system can employtwo-dimensional (2D) image data and/or depth data captured from one ormore 3D sensors (e.g., laser scanners, structured light systems,time-of-flight systems, etc.) to automatically and/or semi-automaticallygenerate a 3D model of an interior environment (e.g., architecturalspaces, architectural structures, physical objects, . . . ). In oneembodiment, the one or more 3D sensors can be implemented on a camera tocapture (e.g., simultaneously capture) texture data and geometric dataassociated with the interior environment. In another embodiment, the oneor more 3D sensors can be implemented on a mobile device (e.g., asmartphone, etc.) to capture texture data and geometric data associatedwith the interior environment.

A 3D model of an interior environment (e.g., the captured 3D data) cancomprise geometric data and/or texture data. The geometric data cancomprise data points of geometry in addition to comprising texturecoordinates associated with the data points of geometry (e.g., texturecoordinates that indicate how to apply texture data to geometric data).For example, a 3D model of an interior environment (e.g., the captured3D data) can comprise mesh data (e.g., a triangle mesh, a quad mesh, aparametric mesh, etc.), one or more texture-mapped meshes (e.g., one ormore texture-mapped polygonal meshes, etc.), a point cloud, a set ofpoint clouds, surfels and/or other data constructed by employing one ormore 3D sensors. In one example, the captured 3D data can be configuredin a triangle mesh format, a quad mesh format, a surfel format, aparameterized solid format, a geometric primitive format and/or anothertype of format. For example, each vertex of polygon in a texture-mappedmesh can include a UV coordinate for a point in a given texture (e.g., a2D texture), where U and V are axes for the given texture. In anon-limiting example for a triangular mesh, each vertex of a trianglecan include a UV coordinate for a point in a given texture. A triangleformed in the texture by three points of the triangle (e.g., a set ofthree UV coordinates) can be mapped onto a mesh triangle for renderingpurposes. In an aspect, the captured 3D data can be unsegmented captured3D data. For example, the captured 3D data can be 3D data that is notpartitioned and/or processed after being captured by one or more 3Dsensors (e.g., the at least one 3D reconstruction system).

An interior environment (e.g., an indoor environment) can include, butis not limited to, one or more rooms, one or more houses, one or moreapartments, one or more office spaces, one or more construction sites,one or more commercial spaces, other living spaces, other workingspaces, other environment spaces, interiors of buildings, vehicles,vessels, aircrafts, subways, tunnels, crawl spaces, equipment areas,attics, cavities, etc. Furthermore, an interior environment can includephysical objects included in one or more rooms, one or more houses, oneor more apartments, one or more office spaces, one or more constructionsites, one or more commercial spaces, other living spaces, other workingspaces and/or other environment spaces.

The partitioning component 104 can partition the captured 3D data. Forexample, the partitioning component 104 can divide the captured 3D datainto one or more data chunks (e.g., one or more data partitions, one ormore data segments, etc.). A data chunk can be a chunk of a 3D model ora particular region (e.g., subsection) of a 3D model. Each of the one ormore data chunks can comprise one or more levels of detail for geometryand/or one or more levels of detail for texture (e.g., visual texture).In one example, each of the one or more data chunks can include multiplelevels of detail for geometry and/or multiple levels of detail fortexture. Therefore, a data chunk can include a hierarchical structure(e.g., a hierarchical structure associated with multiple levels ofdetail). In another example, the partitioning component 104 can generatea single data chunk for the 3D model. The single data chunk for the 3Dmodel can be associated with a plurality of sub-chunks. Each of theplurality of sub-chunks can be a higher resolution than the single datachunk for the 3D model. In an aspect, the partitioning component 104 canpartition the captured 3D data into at least one data chunk associatedwith at least a first level of detail and a second level of detail. Theone or more data chunks and/or the levels of detail can provide greaterflexibility when transmitting 3D data to a remote client device (e.g.,when rending and/or loading a 3D model on a remote client device). In anaspect, the partitioning component 104 can assign an identifier (e.g.,an identifier value, a tag, etc.) to each of the one or more data chunks(e.g., to identify and/or describe each data chunk).

The partitioning component 104 can identify (e.g., automaticallyidentify) architectural elements associated with the captured 3D data(e.g., the 3D model). Architectural elements can include, but are notlimited to, walls, floors, rooms, physical objects, etc. included in the3D model. The partitioning component 104 can partition captured 3D datainto at least one data chunk based on architectural elements (e.g.,identified architectural elements) of a 3D model. For example, the oneor more data chunks can correspond to one or more subsections (e.g., oneor more architectural subsections, one or more architectural elements,etc.) of a 3D model (e.g., captured 3D data, etc.). In an aspect, a datachunk can comprise a flat structure, where each part of the 3D model(e.g., a triangle in a mesh, a region of space in the 3D model, asubsection of the 3D model, etc.) is associated with a single datachunk. For example, the partitioning component 104 can divide a 3D modelof an architectural structure (e.g., a house, etc.) into ‘rooms’, whereeach ‘room’ is associated with a single data chunk. Therefore, thepartitioning component 104 can associate at least one data chunk with aroom included in a 3D model of an interior environment (e.g., a datachunk can be a data chunk of a room in a house).

In another aspect, each of the one or more data chunks can comprise ahierarchical data structure. For example, a data chunk can comprise atree-like data structure associated with levels of detail. In yetanother aspect, a particular data chunk can partially include,completely include, or replace other data chunks, e.g., in a tree-likedata structure. In one example, one or more data chunks can beassociated with a hierarchical data structure. In another example, anoctree data structure can be implemented to hierarchically dividecaptured 3D data (e.g., a 3D model) into one or more data chunks (e.g.,to form a tree data structure). For example, the partitioning component104 can divide captured 3D data into one or more data chunks based on atree data structure (e.g., an octree data structure). In an octree datastructure, a particular data chunk, if not a leaf, can comprise up toeight children (e.g., eight associated data chunks, eight sub-chunks,etc.) which together can cover the same region of space in theparticular data chunk. In one example, the eight children can correspondto eight blocks of data formed by subdividing a data chunk via planesaligned to three axes and centered on a center of a data chunk. Inanother example, multiple data chunks can share the same images oftexture data. For example, one or more data chunks that are determinedto be related based on a hierarchical data structure can be associatedwith the same texture data.

In an aspect, the selection component 106 can select a lowest resolutiondata chunk as an initial data chunk. In one example, a selected lowestresolution data chunk can comprise a different data structure than otherdata chunks. In another example, a selected lowest resolution data chunkcan comprise a lowest mesh complexity and/or a lowest textureresolution. In yet another example, a selected lowest resolution datachunk can comprise flat images with associated position data. Theselection component 106 can select a lowest-detail data chunk (e.g., aunique lowest-detail data chunk) that can be loaded on a remote clientdevice as an initial data chunk for the 3D model.

In one embodiment, an initial data chunk can be a 3D model thatcomprises a certain number of flat planes (e.g., a minimal number offlat planes). One or more flat planes can correspond to each wall, eachfloor, and/or each ceiling in a 3D model. Furthermore, each flat planecan be textured by selecting a point of view in the middle of each roomor near a wall. A scene from a perspective of the selected point of viewcan be projected onto the flat plane representing the wall, floor, orceiling using data from a 3D model (e.g., a full-resolution 3D model).Accordingly, a 3D model can be processed with a lower polygon countand/or a minimal number of textures (e.g., polygon count and/or texturesfor a 3D model can be reduced). In an aspect, texture size can befurther reduced by applying texture compression, selecting a singleaverage color for each of the flat planes, or other techniques. Inanother aspect, flat planes can be expanded to overlap at edges and/orcorners (e.g., to visually indicate a low resolution version of a 3Dmodel, to allow a room to be viewed with fewer amounts of missing dataprior to transmitting and/or loading 3D data associated with furniture,etc.).

In another embodiment, an initial data chunk can be a single texturewhich will be rendered on a ground plane for a 3D model. For example, aninitial data chunk can correspond to a single mesh object (e.g., asingle rectangular mesh object that is textured by a single rectangulartexture). In an aspect, the texture for the single mesh object can be abirds-eye view of an architectural structure (e.g., house), or abirds-eye view of an interior space of an architectural structure (e.g.,house). For example, a birds-eye view can be an orthographic projectionof a 3D model onto a ground plane. In one example, back-face culling canbe applied to the single mesh object so that a floor and/or otherupwards facing surfaces (e.g., tabletops, counters, etc.) for a room inthe architectural structure appear without also including a ceiling ofthe room in a projected image of a 3D model.

In an aspect, an initial chunk can be divided into a set of data chunksthat together comprise a 3D model. For example, a data chunk cancomprise physical boundaries that match or approximately matchboundaries of a higher resolution data chunk or a set of higherresolution data chunks of the 3D model. Thus, as higher resolution datachunks are selected by the selection component 106 and/or transmitted bythe output component 108, a data chunk can be removed from a display ofa remote client device once all of the higher-resolution chunkscorresponding to the same portion of the 3D model are also selected bythe selection component 106 and/or transmitted by the output component108.

It is to be appreciated that the partitioning component 104 canpartition 3D data (e.g., generate one or more data chunks) in a varietyof ways. It is also to be appreciated that the partitioning component104 can combine and/or nest a particular partitioning technique withother partitioning techniques. Furthermore, it is to be appreciated thatthe partitioning component 104 can apply different partitioningtechniques to different 3D models based on composition of a 3D model.

In an aspect, the partitioning component 104 can divide captured 3D data(e.g., a 3D model) into a number of regularly spaced data blocks with afixed height and/or a fixed width. For example, data blocks can comprise(X,Y,Z) dimensions that correspond to width, length and height.Furthermore, the data blocks can be configured as space-filling patternsso that a center of a data block can comprise a coordinate of (a*width,b*length, c*height), where a, b and c are integers. Thus, X coordinatescan be multiples of width, Y coordinates can be multiples of length, andZ coordinates can be multiples of height. Furthermore, each data blockcan correspond to a data chunk. Polygons (e.g., triangles, othergeometry, etc.) that are included in (e.g., entirely within) a datablock can be contained in a corresponding data chunk. Furthermore,polygons (e.g., triangles, other geometry, etc.) which are included inmore than one data block can be assigned to a particular correspondingdata chunk. In an aspect, a data chunk that does not include geometrycan be discarded and/or designated as empty in a data tree structure. Inanother aspect, geometry that is included in more than one data block(e.g., which crosses from one data block to another data block) can besubdivided. For example, a triangle can be subdivided so that eachcomponent of the triangle is included (e.g., wholly included) within onedata block. As such, sub-geometries can be assigned to data chunkscorresponding to data blocks which fully contain the sub-geometry.

In another aspect, the partitioning component 104 can divide captured 3Ddata into one or more data chunks based on a Quad+Z tree data structure.For example, captured 3D data associated with a 3D model can compriseone or more floors of an architectural structure (e.g., a building,etc.). As such, a 3D model can be partitioned by employing a 2D grid inan X-Y plane (e.g., a horizontal plane). Therefore, volume encompassedby a data chunk can be a rectangular prism of infinite height, arectangular prism corresponding to height of a single floor, etc. Assuch, an entire portion of a 3D model above and below a given square orrectangle in a horizontal plane can be included in a particular datachunk. In an aspect, a plane can be divided into 2D blocks. As such,geometry can be assigned to data chunks corresponding to each data blockof the plane. Furthermore, the data blocks can be further subdivided ina hierarchical data structure.

The partitioning component 104 can divide captured 3D data into one ormore data chunks based on subsections (e.g., rooms, cells, etc.) of thecaptured 3D data. For example, a subsection (e.g., a room, a cell, etc.)in a 3D model that is generated based on a scan of an interior space(e.g., by employing one or more 3D sensors) can be identified (e.g.,automatically identified) and/or utilized (e.g., automatically utilized)as a data chunk for the 3D model. In an aspect, a subsection (e.g., aroom, a cell, etc.) can be identified based on a cell and portal method(e.g., a volumetric cell and portal method, portal culling, etc.). Forexample, a volumetric representation of a 3D model can be employed tofacilitate identifying subsections (e.g., rooms, cells, etc.) in the 3Dmodel. Objects in the 3D model to separate can correspond to cells andseparators in the 3D model can correspond to portals.

Once subsections (e.g., rooms, cells, etc.) are identified, thepartitioning component 104 can divide a 3D model so that the set ofgeometry contained in or abutting each subsection corresponds to a datachunk. The partitioning component 104 can continue subdividing a 3Dmodel until a particular threshold score (e.g., threshold value) foradditional divisions is reached. Once the particular threshold score forthe additional divisions is reached, each subdivided section cancorrespond to a unique data chunk. A non-limiting example of adecomposition process associated with a 3D model 400 in a top-down viewis shown in FIG. 4. For example, 3D model 400 includes a subsection(e.g., a room, a cell, etc.) 401, a subsection (e.g., a room, a cell,etc.) 402, and a subsection (e.g., a room, a cell, etc.) 403. 3D model400 also includes a portal (e.g., a division) 404 and a portal (e.g., adivision) 405. For example, a portal can be a division betweensubsections (e.g., between rooms, between cells, etc.). In an aspect,the subsection 401, the subsection 402 and/or the subsection 403 can befurther subdivided into data chunks and/or hierarchical sets of sub-datachunks based on one or more partitioning techniques. The 3D model 400can correspond to partitioned (e.g., processed) 3D data.

Physical objects can be included within each subsection (e.g., withinsubsection 401, subsection 402 and/or subsection 403). For example, aphysical object 406 can be identified (e.g., automatically identified)and/or separated (e.g., automatically separated) as a unique data chunkwithin the subsection 402. A physical object can include, but is notlimited to, furniture, other mobile objects, etc. In an aspect, physicalobjects can be connected to (e.g., associated with) a particularsubsection as a connected component. It is to be appreciated that the 3Dmodel 400 can include more than one physical object. Additionally, thepartitioning component 104 can identify walls and/or floors as prominentplanes in the 3D model 400. After the partitioning component 104identifies walls and/or floors as prominent planes in the 3D model 400and/or associates the prominent planes (e.g., the identified wallsand/or floors) as individual data chunks, the partitioning component 104can remove the identified walls and/or floors from geometry (e.g.,captured 3D data) yet to be assigned to a data chunk. Remainingconnected components in the 3D model 400 can be physical objects (e.g.,couches, tables, lamps desks, other furniture, etc.). As such, eachconnected component can be assigned to a unique data chunk. Additionallyor alternatively, other techniques (e.g., graph-theory concept ofminimum cut, etc.) can be applied to further subdivide remainingportions of the 3D model 400.

The partitioning component 104 can divide captured 3D data into one ormore data chunks based on content type. For example, understandingand/or segmentation of captured 3D data (e.g., a 3D model) can beimplemented as a basis for partitioning the captured 3D data (e.g., the3D model). In one example, the partitioning component 104 can dividecaptured 3D data into one or more data chunks based on volumetric graphcuts, minimal surfaces, active 3D scene segmentation, virtualexploration of a 3D scene, etc. However, it is to be appreciated thatthe partitioning component 104 can divide captured 3D data into one ormore data chunks based on a different technique. In an aspect, thepartitioning component 104 can identify walls, floors and/or ceilings incaptured 3D data by identifying planes within a mesh. For example,planes that comprise a particular size and/or a particular angle (e.g.,an angle corresponding to walls, floors, or ceilings) can be identifiedas walls, floors and/or ceilings (e.g., a prominent plane). In oneexample, the partitioning component 104 can identify walls, floorsand/or ceilings in captured 3D data based on an iterative method suchas, for example, RANdom SAmple Consensus (RANSAC). For example, thepartitioning component 104 can select a certain surface area and/or acertain number of edges, vertices, or triangles that are associated witha common plane. Furthermore, the partitioning component 104 can identifyother points, vertices, or triangles that are also associated with thecommon plane. As such, the partitioning component 104 can determine thata common plane is a prominent plane (e.g., a wall, floor or ceiling) inresponse to a determination that a certain surface area or a certainnumber of edges, vertices, or triangles are associated with the commonplane. Furthermore, the partitioning component 104 can remove geometryassociated with the common plane. Moreover, the partitioning component104 can repeat this process to identify other planes (e.g., other walls,floor or ceilings) in captured 3D data.

In one example, when the partitioning component 104 identifies andremoves each plane from captured 3D data, connected components remainingin the captured 3D data can include physical objects, such as, but notlimited to, tables, chairs, couches, desks, other furniture, etc. Assuch, the partitioning component 104 can assign each connected component(e.g., each physical object) of the captured 3D data to a unique datachunk. Additionally or alternatively, the partitioning component 104 cangroup connected components (e.g., physical objects) associated withcaptured 3D data. For example, connected components (e.g., physicalobjects) can be grouped by subsection (e.g., room). In another example,connected components (e.g., physical objects) can be grouped into asingle “room content” data chunk. Each of the connected components(e.g., physical objects) included in the single “room content” datachunk can be associated with a set of sub-chunks (e.g., a data chunkhierarchy). For example, each sub-chunk in a set of sub-chunks can beassociated with a different degree of resolution (e.g., a differentlevel of detail). In an aspect, the partitioning component 104 canseparate identified planes into data chunks with each connectedcomponent of each identified plane forming a unique data chunk.Additionally or alternatively, the partitioning component 104 can mergeidentified planes and/or connected components (e.g., physical objects)into a smaller number of data chunks. In another aspect, planes can besubdivided at subsection boundaries (e.g., room boundaries) or otherlocations in captured 3D data identified by employing subsectionidentification techniques (e.g., cell and portal methods, etc.).

In a non-limiting example as shown in FIG. 4, after identifying aseparation between each subsection (e.g., each room), planes of thesubsection 402 (e.g. walls and floors associated with a room) can becombined together into a single data chunk. Furthermore, remaininggeometry within the volume of the subsection 402 can include a physicalobject 406 (e.g., a connected component such as, for example, a table).As such, the physical object 406 (e.g., geometry remaining in thecaptured 3D data) can form a single connected component. Furthermore,the physical object 406 can be assigned a unique data chunk.

In one example, one or more hole-filling techniques can be implementedto fill in missing data associated with captured 3D data. For example,geometry data and/or texture data for an occluded area can be missingwhen an area on a wall, floor, or other surface is occluded by anobject. As such, one or more hole-filling techniques can be implementedto generate geometry data and/or texture data for an occluded area. Inone example, a hole associated with a hole boundary that is within acertain distance from being planar can be filled geometrically byrepeatedly connecting pairs of vertices that are two steps along thehole boundary to form triangles until the entire hole is triangulated.Visual data from the 3D reconstruction system can then be projected intotwo dimensions along an axis perpendicular to a determined plane (e.g.,a best-fit plane) to the hole. Alternatively, texture data from an areaaround the hole can be blended according to a weighted average based ondistance to provide visual data for the hole (e.g., missing dataincluded in the hole). Alternatively, the texture of the area around thehole can be provided as input into a texture synthesis algorithm to fillin missing data associated with the hole.

In an aspect, the partitioning component 104 can divide captured 3D datainto one or more data chunks based on subsections (e.g., rooms, cells,etc.) of the captured 3D data and content type. For example, thepartitioning component 104 can divide a 3D model into one or moresubsections (e.g., rooms). Furthermore, the partitioning component 104can further divide each subsection (e.g., each room) into a set ofarchitectural structures (e.g., walls, floors, ceilings, etc.) and intoa set of physical objects (e.g., furniture, etc.) within each subsection(e.g., each room). In one example, the set of objects in each subsectioncan be associated with a single data chunk. In another example, the setof objects in each subsection can be subdivided into a plurality of datachunks. For example, each physical object in a subsection can comprise aunique data chunk. Furthermore, walls, floors, and/or ceilings of asubsection can comprise another data chunk. In one example, walls,floors, and/or ceilings can comprise a unique data chunk. In anotherexample, walls, floors, and/or ceilings can be subdivided into aplurality of data chunks.

The data component 105 can store 3D data processed by the partitioningcomponent 104. For example, the data component 105 can store segmented3D data generated by the partitioning component 104. The data component105 can be implemented as and/or associated with a data structure forstoring one or more data chunks. In one example, the data component 105can be a 3D data component. The data component 105 can store 3D dataincluding levels of detail for each data chunk generated by thepartitioning component 104. In an aspect, the data component 105 canstore a hierarchy of data chunks. For example, the data component 105can store multiple levels of detail for each data chunk.

The selection component 106 can select a data chunk and/or a level ofdetail for a data chunk from the data component 105. In an aspect, theselection component 106 can select a data chunk and/or a portion of datafrom at least one data chunk that is associated with at least a firstlevel of detail and a second level of detail. For example, the selectioncomponent 106 can determine an order for sending the one or more datachunks and/or levels of detail associated with each data chunk (e.g., anorder for the output component 108 to transmit the one or more datachunks and/or levels of detail associated with each data chunk to aremote client device). In an aspect, the selection component 106 canselect a data chunk from a set of data chunks based on information(e.g., geometry data, texture data, level of detail data, resolutiondata, etc.) associated with each data chunk in the set of data chunks.In another aspect, the selection component 106 can select a portion ofdata from the at least one data chunk that is associated with the firstlevel of detail or the second level of detail based on information(e.g., geometry data, texture data, number of sample data points,resolution data, mesh complexity, texture resolution, etc.) associatedwith the first level of detail and the second level of detail. Theinformation associated with each data chunk in the set of data chunkscan be metadata.

In one embodiment, the partitioning component 104 can receive capturedthree-dimensional (3D) data associated with a 3D model of an interiorenvironment and partition the captured 3D data into a data chunkassociated with a level of detail (e.g., a low resolution data chunk)and a plurality of other data chunks associated with other levels ofdetail (e.g., a plurality of higher resolution sub-chunks). The datacomponent 105 can store 3D data including at least the level of detailfor the data chunk and the other levels of detail for the plurality ofother data chunks. The output component 108 can initially transmit thedata chunk to a remote device and subsequently transmit a portion ofdata from the plurality of other data chunks to the remote device basedon information associated with the other levels of detail. As such, afirst data chunk selected by the selection component 106 can be a lowresolution data chunk for the 3D model (e.g., a low resolution datachunk associated with the entire 3D model). After the selectioncomponent 106 selects the first data chunk, the selection component 106can select one or more of the plurality of higher resolution sub-chunksfor the 3D model. For example, each higher resolution sub-chunk for the3D model can be associated with a subsection of the 3D model. One ormore of the plurality of higher resolution sub-chunks for the 3D modelcan be superimposed onto the first data chunk (e.g., the low resolutiondata chunk for the 3D model). In an aspect, the partitioning component104 can partition the captured 3D data into the plurality of other datachunks based on identified architectural elements of the 3D model. Inanother aspect, the data component 105 can store the other levels ofdetail for the plurality of data chunks at a greater level of detail(e.g., a higher resolution) than the level of detail for the data chunk.

In an aspect, the selection component 106 can employ an adaptive orderto select and/or transmit the one or more data chunks and/or levels ofdetail. For example, the selection component 106 can select a data chunkfrom a set of data chunks and/or levels of detail associated with datachunk based on feedback data (e.g., FEEDBACK DATA shown in FIG. 1).Feedback data can include, but is not limited to position dataassociated with a rendering of the 3D model on the remote client device,orientation data associated with a rendering of the 3D model on theremote client device, etc. A 3D model viewer on the remote client devicecan display the rendering of the 3D model. The feedback data can bereceived from a remote client device (e.g., a remote client device thatrenders the 3D model, a remote client device that employs a 3D modelviewer to display the 3D model, etc.). In one example, an adaptive ordercan be based on the position of a rendered view in a remote clientdevice. In a non-limiting example where a data chunk is associated witha number of discrete detail levels, the selection component 106 caninitially select and/or transmit each data chunk of the lowest detail ina certain fixed order or a certain variable order, then select and/ortransmit each data chunk of the next most detailed level, etc. until ahighest level data chunk is selected and/or transmitted.

The selection component 106 can select and/or transmit one or more datachunks and/or levels of detail based on position data associated with arendered view on a remote client device (e.g., a remote client deviceconfigured for receiving the one or more data chunks and/or displaying a3D model via a 3D model viewer). For example, the selection component106 can select and/or transmit a particular data chunk that is closestto a camera position and/or a camera orientation (e.g., a point of view)associated with a rendering of the 3D model on a remote client device.In one example, the selection component 106 can select and/or transmitthe particular data chunk from lowest level of detail to highest levelof detail, then select and/or transmit a next closest data chunk fromlowest level of detail to highest level of detail, etc. A closest datachunk can be a data chunk that contains a triangle, a surfel, or a pointwhich is closest to a viewpoint associated with a remote client device(e.g., a viewpoint associated with a rendering of the 3D model on aremote client device). Alternatively, a closest data chunk can be a datachunk associated with a smallest average distance across all triangles,surfels, or points associated with the data chunk with respect to aviewpoint associated with a remote client device (e.g., a viewpointassociated with a rendering of the 3D model on a remote client device).In another aspect, the selection component 106 can select and/ortransmit one or more data chunks and/or levels of detail based on avisibility-based culling technique. A visibility-based culling techniquecan include, but not limited to, view-frustum culling, occlusionculling, back-face culling, detail culling, etc. However, it is to beappreciated that the selection component 106 can implement similartechniques to select and/or transmit one or more data chunks and/orlevels of detail.

The selection component 106 can select and/or transmit a portion of dataassociated with a level of detail based on a previously selected levelof detail. In a non-limiting example, the selection component 106 canselect and/or transmit a single chunk with two levels of detailassociated with mesh data and/or texture data. For example, a 3D modelcan comprise a single chunk at multiple levels of detail. As such, theselection component 106 can initially select and/or transmit a lowresolution version of the 3D model. For example, the low resolutionversion of the 3D model can comprise a mesh (e.g., a polygonal mesh)with a small number of triangles (e.g., 20 k) and low resolutiontextures (e.g. ⅛th of the pixel resolution in each dimension of ahighest resolution texture, ⅛th of the pixel resolution in eachdimension of 512×512 pixel images, etc.). In one example, textures canbe encoded (e.g., JPEG encoded) with high compression to further reducesize. After the selection component 106 selects and/or transmits the lowresolution version of the 3D model (e.g., a previously selected versionof the 3D model), the selection component 106 can select and/or transmita high resolution version of the 3D model and/or a full resolutionversion of the 3D model. A higher resolution version of the 3D model cancorrespond to greater mesh complexity and/or greater texture resolution.For example, a high resolution version of the 3D model can comprise amesh (e.g., a polygonal mesh) with a large number of triangles (e.g.,500 k) and/or full resolution textures with little or no compression.

In another non-limiting example, the selection component 106 can selectand/or transmit a single chunk with different texture levels of detailand/or different mesh levels of detail. For example, a 3D model cancomprise a single chunk at multiple levels of detail. As such, theselection component 106 can initially select and/or transmit a lowresolution version of the 3D model. For example, a low resolutionversion of the 3D model can comprise a mesh (e.g., a polygonal mesh)with a certain number of triangles (e.g., a small number of triangles ascompared to other versions of the 3D model) and/or low resolutiontextures associated with a certain amount of compression (e.g., greatercompression as compared to other versions of the 3D model). Next, theselection component 106 can select and/or transmit a high resolutionversion of the 3D model that comprises a mesh (e.g., a polygonal mesh)that employs the low resolution textures associated with the lowresolution version of the 3D model. Next, the selection component 106can select and/or transmit high resolution textures that can be mappedonto a high resolution mesh. For example, high resolution textures cancomprise a highest resolution as compared to other versions of the 3Dmodel (e.g., eight times as many pixels in each dimension as previouslyselected and/or transmitted textures, eight times as many pixels in eachdimension as 2048×2048 pixel images, etc.). Furthermore, high resolutiontextures can comprise less compression as compared to other versions ofthe 3D model (e.g., high resolution textures can be encoded in alossless format, etc.) for better final image quality. It is to beappreciated that these techniques can be extended to more than twolevels of detail (e.g., to allow the selection component 106 to selectand/or transmit progressively higher resolution meshes and/or textures).It is also to be appreciated that ordering employed by the selectioncomponent 106 to select and/or transmit level of detail for meshesand/or textures can be altered. For example, the selection component 106can select and/or transmit high resolution textures prior to higherresolution meshes, etc. In an aspect, prioritization of textures-firstor mesh-first can depend on a position from which a user is viewing the3D model (e.g., a position of a remote client device). For example,textures may be prioritized if a user is viewing the 3D model via a 3Dmodel viewer on a remote client device in greater detail (e.g., upclose, zoomed in, etc.).

In an aspect, a higher-resolution version of a data chunk that isselected and/or transmitted by the selection component 106 can replace alower resolution version of the data chunk in a list of 3D data to bedisplayed (e.g., displayed on a remote client device). In anotheraspect, a data chunk associated with a plurality of sub-chunks (e.g., aplurality of child data chunks with respect to a hierarchical datastructure) can be replaced with one or more data chunks that are alsoassociated with the plurality of sub-chunks (e.g., one or more datachunks associated with the plurality of child data chunks) in responseto a determination that each of the plurality of sub-chunks are selectedand/or transmitted by the selection component 106 (e.g., in response toa determination that each of the plurality of child sub-chunks have beentransmitted to a remote client device). As such, a data chunk can bereplaced in a display of a remote client device with higher-detailsub-chunks once all sub-chunks associated with the data chunk areloaded.

In one embodiment, the selection component 106 can select and/ortransmit the one or more data chunks and/or levels of detail for the oneor more data chunks based on a depth-first in resolution technique. Forexample, the selection component 106 can initially select and/ortransmit a lowest resolution version of each data chunk in the 3D model.Then, the selection component 106 can select and/or transmit a next mostdetailed level for each data chunk, and so on until a highest level ofdetail for each data chunk has been selected and/or transmitted by theselection component 106. In an aspect, ordering within each detail levelcan be arbitrarily (e.g., randomly) determined. In one example, orderingwithin each detail level can be determined based on a random numbergenerator.

In another embodiment, the selection component 106 can select and/ortransmit the one or more data chunks and/or levels of detail for the oneor more data chunks based on a highest resolution only technique. Forexample, the selection component 106 can select and/or transmit ahighest level of detail version of each data chunk without selectingand/or transmitting any lower levels of detail for each data chunk. Inan aspect, the selection component 106 can implement the high resolutiononly technique with other methods to select and/or transmit data chunks(e.g., the high resolution only technique can be combined with othermethods to select data chunks and/or to determine an order fortransmitting data chunks).

In yet another embodiment, the selection component 106 can select and/ortransmit the one or more data chunks and/or levels of detail for the oneor more data chunks based on a view frustum technique. For example, theselection component 106 can compute a view frustum based on positiondata and/or orientation data associated with a viewpoint of a remoteclient device (e.g., a remote client device configured for receiving theone or more data chunks and/or levels of detail for the one or more datachunks). The selection component 106 can determine (e.g., calculate) alist of data chunks that intersect the frustum based on the viewfrustum.

In an aspect, the selection component 106 can sort and/or order datachunks which intersect the frustum (e.g., data chunks which may bevisible) based on distance with respect to the viewpoint of the remoteclient device. For example, the selection component 106 can selectand/or transmit a closest data chunk in the view frustum which has notbeen selected and/or transmitted at a highest resolution. In oneexample, the selection component 106 can update and/or recalculate anordering of data chunks which intersect the frustum when a view frustumchanges. In an example, the selection component 106 can determine aclosest data chunk and/or sort data chunks based on a search technique.For example, the selection component 106 can determine a closest datachunk and/or sort data chunks by employing an octree. In one example,the selection component 106 can determine data chunks that intersectparticular portions (e.g., volumes) of an octree data structure. Datachunks can be stored in an octree data structure. As such, a portion(e.g., a volume) of a view frustum can be employed to query the octreedata structure (e.g., to identify intersecting data chunks).Furthermore, the selection component 106 can analyze intersecting datachunks.

In another aspect, the selection component 106 can compute an angularsize (e.g., an apparent angular size) of each data chunk within thefrustum. For example, the selection component 106 can project a boundingregion (e.g., a bounding cube of a data chunk intersected with thefrustum) to the viewpoint associated with the remote client device. Inone example, the selection component 106 can then order a list of datachunks intersecting the frustum based on the angular size. As such, anext data chunk selected and/or transmitted by the selection component106 is a highest resolution version.

In yet another implementation, the selection component 106 can compute ascore based on resolution of a data chunk and/or a computed angular sizeof the data chunk. For example, a score can be number of pixels orvertices per steradian (e.g., a measure of a solid angle) given acurrent level of detail of the data chunk and distance to the viewpointassociated with the remote client device. In another example, a scorecan be computed as a size of a data chunk (e.g., number of bytes of adata chunk) relative to steradian size of the data chunk from theviewpoint associated with the remote client device. In an aspect, thepartitioning component 104 can select a level of detail for a data chunkwith a lowest score so that a score for the data chunk is no longer alowest score. The selected level of detail for the data chunk can beselected for transmission (e.g., the selected level of detail for thedata chunk can be transmitted next to a remote client device). Inanother aspect, the selection component 106 can select a level of detailfor a data chunk with the lowest score so that a new score for the datachunk is greater than a predetermined threshold value. The selectedlevel of detail for the data chunk can be selected for transmission(e.g., the selected level of detail for the data chunk can betransmitted next to a remote client device). In one example, theselection component 106 can employ a different method to select and/ortransmit a data chunk and/or a level of detail for a data chunk inresponse to a determination that all data chunks are greater than thepredetermined threshold value. In another example, a different thresholdvalue (e.g., a higher threshold value, a greater threshold value, etc.)can be implemented to select and/or transmit a data chunk and/or a levelof detail for a data chunk in response to a determination that all datachunks are greater than the predetermined threshold value (e.g., inresponse to a determination that all data chunks satisfy thepredetermined threshold value).

In yet another embodiment, the selection component 106 can select and/ortransmit the one or more data chunks and/or levels of detail for the oneor more data chunks based on information associated with a 3D modelviewer (e.g., a 3D model viewer implemented on a remote client device).The selection component 106 can select and/or transmit one or more datachunks and/or levels of detail for one or more data chunks that occupy agreatest amount of space in a current view (e.g., a current renderedfield of view) on a 3D model viewer. For example, the selectioncomponent 106 can initially select and/or transmit a lowest resolutionversion of each data chunk in the 3D model. Then, the selectioncomponent 106 can statistically sample and/or determine the number ofcamera rays emitted from a virtual camera (e.g., a virtual cameraassociated with a 3D model viewer implemented on a remote client device)within a current rendered field of view of the 3D model which intersecteach data chunk of the 3D model (e.g., each data chunk of the 3D modelas a first intersection with the 3D model). As such, the selectioncomponent 106 can select and/or transmit a next data chunk and/or a nextlevel of detail for a data chunk based on the number of camera rayswhich intersect each data chunk. For example, a next data chunk and/or anext level of detail for a data chunk to be selected and/or transmittedcan be a higher resolution version of the data chunk (e.g., a resolutionversion of the data chunk that is above a current resolution version ofthe data chunk being displayed on a remote client device) with a highestnumber of camera rays that is not loaded at the highest resolution. Inresponse to a determination that each data chunk comprises more than twolevels of resolution, the number of camera rays which have intersected aparticular data chunk can be combined with a current level of detail ofthe particular data chunk to generate a score. For instance, the scorecan be employed to select and/or transmit a next data chunk and/or anext level of detail. In one example, the level of detail for aparticular data chunk that is selected and/or transmitted can be onelevel of detail higher than a current level of detail for the particulardata chunk. In another example, the level of detail for a particulardata chunk that is selected and/or transmitted can be determined by ascoring function.

If each level of detail for a particular data chunk is twice as detailedin each direction as a previous level of detail for the data chunk, thena score can be determined based on number of camera rays that intersectwith the particular data chunk and a level of detail of the particulardata chunk. In one example, a score can correspond toRAYCOUNT/(4{circumflex over ( )}LOD), where a variable RAYCOUNT isnumber of camera rays (e.g., number of camera rays that emit from acurrent user position on a rendering of the 3D model) that intersectwith a particular data chunk on the 3D model and a variable LOD is alevel of detail of the particular data chunk. For example, the variableRAYCOUNT can be a map from a data chunk identifiers (e.g., where eachdata chunk comprises a unique identifier) to integers. The variableRAYCOUNT can be initialized so that an identifier of each data chunkmaps to an integer zero. The variable LOD can be a map from a data chunkidentifiers to integers, where LOD[i] represents a current level ofdetail in a remote client device of a particular data chunk withidentifier i, where identifier i is a non-negative integer. For example,a value of zero for identifier i can represent no detail in a remoteclient device for a particular data chunk, a value of one for identifieri can represents a first level of detail in the remote client device forthe particular data chunk, etc. Each time a frame is rendered by theremote client device, the number of camera rays intersecting each datachunk as a first intersection with the 3D model can be calculated. Thecalculated number of camera rays for a current frame can be added to theinteger mapped by an identifier for each data chunk. In one example, themap can be received by the selection component 106 from the remoteclient device. As such, the selection component 106 can determine a nextdata chunk to select and/or transmit.

Alternatively, the remote client device can request a next data chunkfrom the data component 105 based on sizes of detail and/or levels ofdetail of a data chunk currently employed by the remote client device.Additionally or alternatively, the remote client device can request anext data chunk from the data component 105 based on a list of datachunks and/or a list of detail levels. In an aspect, a score for a datachunk i is given by RAYCOUNT[i]/4{circumflex over ( )}LOD[i]. For datachunks that are not associated with a highest level of detail, a nextfinest level of detail for a data chunk with a highest score can beselected and/or transmitted. In one example, the camera ray count (e.g.,a count of camera rays intersecting each data chunk) can be replaced bya statistical sample in which a small number of randomly oriented camerarays within a field of view of a rendering of the 3D model on a remoteclient device are employed and/or nearest data chunk intersections ofthe randomly oriented camera rays are tallied. As such, the selectioncomponent 106 can select a data chunk and/or a level of detail based ona total number of camera rays employed to determine data associated witha data chunk. Alternatively, a buffer (e.g., a Z buffer) associated witha graphic component (e.g., a graphic card) on a remote client device canbe utilized as an alternate to casting rays.

In yet another embodiment, the selection component 106 can select and/ortransmit the one or more data chunks and/or levels of detail for the oneor more data chunks based on user behavior when viewing a 3D model(e.g., past behavior of one or more users viewing a 3D model, userhistory, history of position data and/or orientation data, etc.) via a3D model viewer on a remote client device. For example, previouspositions of users (e.g., previous viewing positions of users)associated with a rendering of a 3D model can be employed to speculatefuture positions of users (e.g., likely future viewing positions ofusers). In an example, data chunks that are previously viewed the most(e.g., a most viewed data chunk) can be selected and/or transmitted bythe selection component 106 first. For example, position data and/ororientation data associated with a camera view for viewing a 3D modelvia a 3D model viewer on a remote client device can be stored (e.g., atperiodic intervals). The position data and/or orientation data can forma set of data points associated with a certain portion (e.g., a certainvolume) of the 3D model. The set of data points can be processed (e.g.,smoothed) to generate an average distribution of user locations over thecertain portion (e.g., the certain volume) of the 3D model. As such,highest values of data points associated with the average distributioncan be considered a most likely viewing position for a user.Furthermore, the highest values of data points associated with theaverage distribution (e.g., the most likely viewing position of theuser) can be employed to determine initial data chunks and/or initiallevels of detail to select and/or transmit. Alternatively, highestvalues of data points associated with the average distribution (e.g.,the most likely viewing position of the user) can be employed togenerate a model for predicting future user position and/or future userorientation based on current user position and/or current userorientation. In one example, the model for predicting future userposition and/or future user orientation can be generated based on ahidden Markov model. However, it is to be appreciated that the model forpredicting future user position and/or future user orientation can begenerated based on a different technique. In an aspect, a probabilitydistribution of near-future user positions and/or near-future userorientations (e.g., determined based on current user position and/orcurrent user orientation) can be employed to select and/or transmit anext data chunk, prioritize data chunks that are likely to be near auser within a certain period of time, prioritize data chunks that arelikely to be in a field of view for a 3D model viewer on a remote clientdevice within a certain period of time, etc.

In an aspect, selection and/or transmission of physical objects can bede-prioritized in response to a determination that a 3D model ispartitioned into architectural structures (e.g., walls, etc.) and/orphysical objects contained within an architectural frame (e.g.,furniture, etc.) unless the physical objects are included in the samesubsection (e.g., the same room) as a current position of a user (e.g.,a current position of a remote client device). In an non-limitingexample, if a 3D model is partitioned into one data chunk for walls andfloors of each subsection (e.g., each room), and one or more data chunksfor physical objects of a subsection (e.g., content included in asubsection), then selection and/or transmission priority can be thefollowing: initially select and/or transmit walls and floors of asubsection (e.g., a room) that a camera view of a 3D model viewer iscurrently associated with, followed by physical objects of the currentsubsection (e.g., content included in the current room), followed bywalls and floors of adjacent subsections (e.g., adjacent rooms),followed by physical objects of adjacent subsections (e.g., contentincluded in adjacent rooms), followed by all other walls and floors,followed by all other physical objects (e.g., all other content includedin the 3D model). Data chunks can be selected and/or transmitted by theselection component 106 in priority order. In an aspect, ordering of theselection and/or transmission of data chunks can be updated periodicallybased on changes in a position of a camera view of a 3D model viewer.Additionally or alternatively, a priority ordering of data chunks at aparticular level of detail can be determined for data chunks comprisingmultiple levels of detail.

It is to be appreciated that captured 3D data can be received by theselection component 106 and/or the output component 108 without beingpartitioned by the partitioning component 104. For example, captured 3Ddata can be transmitted to a remote client device without beingpartitioned into one or more data chunks and/or one or more levels ofdetail.

The output component 108 can transmit processed 3D data (e.g., PROCESSED3D DATA shown in FIG. 1) to a remote client device. The remote clientdevice can be configured to render and/or display a 3D model associatedwith the processed 3D data (e.g., via a 3D model viewer). For example,the output component 108 can transmit one or more data chunks and/or oneor more levels of detail for data chunks based on an ordering (e.g., atransmission order) determined by the selection component 106. In oneexample, the processed 3D data can be processed 3D-reconstructed data.

In an aspect, the output component 108 can generate one or more visualeffects for data chunks (e.g., high resolution data chunks) and/orlevels of detail transmitted to a remote client device. In one example,the output component 108 can generate one or more visual effects for ahigh resolution data chunk (e.g., when transmitting a high resolutiondata chunk) after a flat data chunk or a low resolution data chunk isrendered by a remote client device (e.g., for display on a 3D modelviewer). For example, a high resolution data chunk associated with asubsection of a 3D model (e.g., a room) can be rendered on the remoteclient device as rising out of a floor in the 3D model, as dropping fromabove the 3D model, as expanding from a particular point in the 3Dmodel, as resembling an unstable state (e.g., blowing up and wobblinglike jelly, etc.) before stabilizing in a final position in the 3Dmodel, etc.

In another aspect, the output component 108 can generate a visualindication that a particular data chunk is not at a highest level ofdetail. For example, the output component 108 can generate an indicationfor a remote client device (e.g., a 3D model viewer implemented on aremote client device) that at least a portion of the 3D model is not ata highest available resolution. Furthermore, the output component 108can generate an indication for a remote client device that a higherresolution version will be provided to the remote client device.

In one example, the output component 108 can generate a watermark for alow-resolution texture and/or append (e.g., superimpose) a watermark ontextures associated with at least a portion of a data chunk that is notat a highest level of detail. In an example, a watermark can be appliedin a regular pattern to textures which cover flat surfaces of a certainsize. For example, walls and/or floors of a data chunk associated with aroom can comprise watermarks, but physical objects (e.g., furniture) canbe implemented without a watermark. In an aspect, a watermark can beanimated with respect to time.

In another example, the output component 108 can configure a data chunkwith a reduced alpha level so that other objects are visible through thedata chunk. For example, a data chunk at a medium level of detail cancomprise an alpha level of 70% (e.g., an alpha level where a data chunkis partially see-through, but mostly resembling a solid), while any datachunks at a highest level of detail comprise an alpha level of 100%(e.g., an alpha level where a data chunk is completely opaque).

In yet another example, the output component 108 can configure a datachunk to blink or smoothly interpolate over time in a cyclical fashion.For example, the output component 108 can configure a data chunk toalter between a full alpha level of 100% and an alpha level less than100%. Additionally or alternatively, the output component 108 canconfigure color, brightness, hue, and/or saturation of a data chunk toalter in a cyclical fashion. In yet another example, the outputcomponent 108 can configure texture of a data chunk with differentcolor, brightness, hue, and/or saturation. For example, the outputcomponent 108 can configure texture of a data chunk with lower levels ofdetail to be displayed as grayscale. In yet another example, the outputcomponent 108 can configure a data chunk with no texture (e.g., withouttexture). In yet another example, the output component 108 can configurea data chunk with a grid (e.g., a grid can be projected on a datachunk). In yet another example, the output component 108 can configure adata chunk (e.g., a data chunk to be displayed on a remote clientdevice) with superimposed vertically or horizontally moving lines tosuggest that a scanning operation for the data chunk is in progress. Inyet another example, the output component 108 can generate a message(e.g., a loading message) in response to a determination that a portionof a 3D model is loading. Additionally or alternatively, the outputcomponent 108 can generate a message (e.g., a loading message) inresponse to a determination that a portion of the 3D model currentlybeing displayed via a 3D model viewer on a remote client device is notat a highest possible level of detail.

In an aspect, the output component 108 can generate a projection of aportion of a 3D model (e.g., a 3D scene) where level of detail has notbeen provided for data chunks. In an example, the output component 108can determine a point of projection to display an unloaded data chunk.For example, if a data chunk is a room, then a point of projection canbe determined to be a point just outside a door to that room. In oneexample, projections can be displayed on flat planes located in the 3Dmodel. For example, projections can be displayed at the portals (e.g.,404, 405) of unloaded subsections (e.g., 401, 402, 403). In anotherexample, projections can be displayed as skyboxes within the 3D model.

While FIG. 1 depicts separate components in system 100, it is to beappreciated that the components may be implemented in a commoncomponent. In one example, the partitioning component 104, the datacomponent 105, the selection component 106 and/or the output component108 can be included in a single component. Further, it can beappreciated that the design of system 100 can include other componentselections, component placements, etc., to facilitate processing and/ortransmitting 3D data.

Referring to FIG. 2, there is illustrated a non-limiting implementationof a system 200 in accordance with various aspects and implementationsof this disclosure. The system includes at least one server 202, anetwork 204 and a remote client device 206. The at least one server 202can include at least the processing component 102. The processingcomponent 102 can include the partitioning component 104, the datacomponent 105, the selection component 106 and/or the output component108.

The remote client device 206 can be configured to receive 3D data (e.g.,processed 3D data, processed 3D-reconstructed data, etc.) to renderand/or display a 3D model. A 3D model can be displayed on the remoteclient device 206 via a 3D model viewer. Additionally, the remote clientdevice 206 can determine position data and/or orientation data (e.g.,feedback data) associated with a viewpoint and/or a camera position of arendering of a 3D model on the 3D model viewer. The remote client device206 can transmit the position data and/or orientation data (e.g.,feedback data) to the at least one server 202. In an aspect, the atleast one server 202 can be associated with a 3D reconstruction system.In another aspect, the remote client device 206 can be associated with auser (e.g., a user identity, etc.). The remote client device 206 caninclude, but is not limited to, a cellular phone (e.g., a smart phone),a tablet, a personal computer (PC), a desktop computer, a laptopcomputer, a camera, a 3D capture system, another portable computingdevice, etc. The at least one server 202 can be communicably coupled tothe remote client device 206 via the network 204. The network 204 caninclude one or more networks. For example, network 204 can include oneor more wireless networks and/or one or more wired networks, includingbut not limited to, a cellular network, a wide area network (WAN, e.g.,the Internet), a local area network (LAN) and/or a personal area network(PAN). In an example, the at least one server 202 (e.g., the processingcomponent 102) can transmit processed 3D data to the remote clientdevice 206 via the network 204. As such, the remote client device 206can receive processed 3D data via virtually any desired wireless orwired technology, including, for example, cellular, WAN, wirelessfidelity, etc.

The at least one server 202 (e.g., the processing component 102) canprocess and/or transmit 3D data, as more fully disclosed herein. Forexample, in an aspect, the at least one server 202 (e.g., the processingcomponent 102) can partition 3D data associated with a 3D model into atleast one data chunk associated with multiple levels of detail.Furthermore, the at least one server 202 (e.g., the processing component102) can determine a transmission order for the multiple levels ofdetail associated with the at least one data chunk based on dataassociated with the multiple levels of detail. In an aspect, the atleast one server 202 (e.g., the processing component 102) can furtherdetermine the transmission order for the multiple levels of detailassociated with the at least one data chunk based on feedback data(e.g., position data and/or orientation data) and/or a transmissionorder of data chunks associated with the remote client device 206. Inone example, the data associated with the multiple levels of detail cancomprise geometric data and/or texture data. In another aspect, the atleast one server 202 can transmit information associated with datachunks and/or levels of detail (e.g., size information of data chunks,hierarchy information for data chunks, etc.) to the remote client device206.

The remote client device 206 can receive the multiple levels of detailassociated with the at least one data chunk and/or multiple data chunksfrom the at least one server 202 (e.g., the processing component 102)based on the transmission order. In an aspect, the remote client device206 can receive the multiple levels of detail from lowest level ofdetail to highest level of detail. Furthermore, the remote client device206 can render at least a portion of the 3D model based on the multiplelevels of detail associated with the at least one data chunk.

In an example, the at least one server 202 (e.g., the processingcomponent 102) can receive and/or store captured 3D data associated witha 3D model. The at least one server 202 can partition the captured 3Ddata into one or more data chunks (e.g., based on identifiedarchitectural elements of the 3D model). Furthermore, the remote clientdevice 206 can receive data chunks generated by the at least one server202 and/or render the data chunks received from the at least one server202. A user can view a rendered 3D model via a 3D model viewer on theremote client device 206 once the remote client device 206 receivesenough data chunks to construct the rendered 3D model on the 3D modelviewer. As a camera view associated with the rendered 3D model on the 3Dmodel viewer varies, the at least one server 202 can transmit new datachunks to the remote client device 206. In an aspect, the at least oneserver 202 can transmit new data chunks to the remote client device 206based on position data and/or orientation data associated with thecamera view (e.g., the camera view associated with the rendered 3D modelon the 3D model viewer). It is to be appreciated that the at least oneserver 202 (e.g., the processing component 102) and/or the remote clientdevice 206 can include other features and/or be associated with othertechniques for processing and/or transmitting 3D data, as more fullydisclosed herein.

Referring to FIG. 3, there is illustrated a non-limiting implementationof a system 300 in accordance with various aspects and implementationsof this disclosure. The system includes the at least one server 202, thenetwork 204 and the remote client device 206. The at least one server202 can include at least the partitioning component 104, the datacomponent 105 and/or the output component 108. The remote client device206 can include at least the selection component 106.

The partitioning component 104, the data component 105 and/or the outputcomponent 108 implemented on the at least one server 202 can processand/or transmit 3D data, as more fully disclosed herein. In an aspect,the at least one server 202 can partition 3D data associated with a 3Dmodel of an interior environment into at least one data chunk associatedwith multiple levels of detail, store the multiple levels of detailassociated with the at least one data chunk in a data structure, and/ortransmit the multiple levels of detail associated with the at least onedata chunk to a remote device based on a transmission order determinedas a function of data associated with the multiple levels of detail.

The remote client device 206 can determine the transmission order forthe multiple levels of detail associated with the at least one datachunk based on the data associated with the levels of detail, receivethe multiple levels of detail associated with the at least one datachunk from the server based on the transmission order, and/or render atleast a portion of the 3D model based on the multiple levels of detailassociated with the at least one data chunk. In an aspect, the remoteclient device 206 can request a particular data chunk and/or aparticular level of detail for a data chunk stored in the data component105 (e.g., send a request to the at least one server 202 that includesinformation regarding a particular data chunk and/or a particular levelof detail for a data chunk) based on the determined transmission order.The remote client device 206 can load requested data chunks and/orrequested levels of detail via a 3D model viewer associated with theremote client device 206.

The at least one server 202 can transmit information associated withdata chunks and/or the levels of detail to the remote client device 206(e.g., the selection component 106 implemented on the remote clientdevice 206) to facilitate selection of a data chunk and/or a level ofdetail associated with a data chunk. The information can include, but isnot limited to size information for the data chunks, positioninformation for data chunks, level of detail information for datachunks, etc. In one example, the at least one server 202 can transmit ahierarchy index associated with the data component 105 to the remoteclient device 206. A hierarchy index can be an index of data chunksand/or levels of detail stored in the data component 105. As such, theremote client device 206 can determine a transmission order based on theinformation and/or the hierarchy index received from the at least oneserver 202. It is to be appreciated that the selection component 106implemented on the remote client device 206 can additionally oralternatively implement other features and/or be associated with othertechniques for selecting a data chunk and/or a level of detailassociated with a data chunk, as more fully disclosed herein.

The aforementioned systems and/or devices have been described withrespect to interaction between several components. It should beappreciated that such systems and components can include thosecomponents or sub-components specified therein, some of the specifiedcomponents or sub-components, and/or additional components.Sub-components could also be implemented as components communicativelycoupled to other components rather than included within parentcomponents. Further yet, one or more components and/or sub-componentsmay be combined into a single component providing aggregatefunctionality. The components may also interact with one or more othercomponents not specifically described herein for the sake of brevity,but known by those of skill in the art.

FIGS. 5-9 illustrate methodologies and/or flow diagrams in accordancewith the disclosed subject matter. For simplicity of explanation, themethodologies are depicted and described as a series of acts. It is tobe understood and appreciated that the subject innovation is not limitedby the acts illustrated and/or by the order of acts, for example actscan occur in various orders and/or concurrently, and with other acts notpresented and described herein. Furthermore, not all illustrated actsmay be required to implement the methodologies in accordance with thedisclosed subject matter. In addition, those skilled in the art willunderstand and appreciate that the methodologies could alternatively berepresented as a series of interrelated states via a state diagram orevents. Additionally, it should be further appreciated that themethodologies disclosed hereinafter and throughout this specificationare capable of being stored on an article of manufacture to facilitatetransporting and transferring such methodologies to computers. The termarticle of manufacture, as used herein, is intended to encompass acomputer program accessible from any computer-readable device or storagemedia.

Referring to FIG. 5, there illustrated is a methodology 500 forprocessing and/or transmitting 3D data, according to an aspect of thesubject innovation. As an example, methodology 500 can be utilized invarious applications, such as, but not limited to, 3D modeling systems,3D reconstruction systems, server systems, cloud-based systems, etc. At502, three-dimensional (3D) data associated with a 3D model of aninterior environment is stored (e.g., by at least one server 202). At504, the 3D data is partitioned into at least one data chunk (e.g., byat least one server 202) based on identified architectural elements ofthe 3D model. At 506, the plurality of data chunks are sent to a remotedevice (e.g., by at least one server 202) based on a determinedtransmission order. Additionally or alternatively, informationassociated with the plurality of data chunks are sent to the remotedevice (e.g., by at least one server 202). For example, informationassociated with the plurality of data chunks can include, but is notlimited to, size information for the plurality of data chunks, positioninformation for the plurality of data chunks, hierarchy information(e.g., level of detail information) for the plurality of data chunks,etc. At 508, one or more new data chunks are sent to the remote device(e.g., by at least one server 202) based on the information associatedwith the plurality of data chunks, other information associated with arendering of the 3D model on the remote device and/or other informationassociated with a camera position in the rendering of the 3D model onthe remote device.

Referring to FIG. 6, there illustrated is a methodology 600 forprocessing and/or transmitting 3D data, according to another aspect ofthe subject innovation. At 602, three-dimensional (3D) data associatedwith a 3D model for an environment is received (e.g., by a processingcomponent 102 and/or a partitioning component 104). At 604, the 3D datais partitioned into at least one data chunk (e.g., by a partitioningcomponent 104) based on one or more data chunking techniques. At 606, atransmission order for the at least one data chunk, geometry dataassociated with the at least one data chunk, and/or texture dataassociated with the at least one data chunk is determined (e.g., by aselection component 106). At 608, the at least one data chunk, thegeometry data associated with the at least one data chunk, and/or thetexture data associated with the at least one data chunk is sent to aremote device (e.g., by an output component 108) based on thetransmission order.

Referring to FIG. 7, there illustrated is a methodology 700 forprocessing and/or transmitting 3D data, according to yet another aspectof the subject innovation. At 702, captured three-dimensional (3D) dataassociated with a 3D model of an interior environment is received (e.g.,by a processing component 102 and/or a partitioning component 104). At704, the captured 3D data is partitioned into at least one data segmentassociated with multiple levels of detail (e.g., using a partitioningcomponent 104). At 706, 3D data including the multiple levels of detailassociated with the at least one data segment is stored in a datastructure (e.g., by a data component 105). At 708, the multiple levelsof detail for the at least one data segment are transmitted to a remotedevice (e.g., by an output component 108) based on an order determinedas a function of geometry data and/or texture data associated with themultiple levels of detail.

Referring to FIG. 8, there illustrated is a methodology 800 forprocessing and/or transmitting 3D data, according to yet another aspectof the subject innovation. At 802, captured three-dimensional (3D) dataassociated with a 3D model is received (e.g., by a processing component102 and/or a partitioning component 104). At 804, the captured 3D datais divided into at least one data chunk associated with multiple levelsof detail (e.g., using a partitioning component 104). At 806, an orderto transmit the multiple levels of detail for the at least one datachunk is selected (e.g., using a selection component 106) based at leaston position data and/or orientation data associated with a rendering ofthe 3D model on the remote device. At 808, the multiple levels of detailfor the at least one data chunk are sent to the remote device (e.g., byan output component 108) based on the order.

Referring to FIG. 9, there illustrated is an example methodology 900 forsending data chunks from a server to a remote client device based onview position, according to an aspect of the subject innovation. Forexample, methodology 900 shows an example communication flow between aremote client device and a server for selecting a particular level ofdetail and/or a particular data chunk based on feedback from the remoteclient device (e.g., a position of a camera associated with the remoteclient device). At 902, a client requests a mesh from a server. Forexample, a remote client device can request 3D data from a server. In anaspect, the remote client device can send an initial position of a userin a rendering of a 3D model (e.g., a viewing position associated with aweb-based viewer implemented on the remote client device). As such, aninitial mesh sent from the server to the client can be chosen to moreaccurately correspond to an initial viewpoint associated with theclient. At 904, a low-resolution mesh is sent from the server to theclient. For example, the server can send initial data regarding the mesh(e.g., a data chunk or a collection of data chunks representing a lowresolution version of the mesh and/or textures associated with the 3Ddata) to the remote client device (e.g., to be initially displayed onthe remote client device). At 906, the client reports a user position tothe server. For example, the remote client device can report a positionof a user in a rendering of a 3D model (e.g., a viewing positionassociated with a viewer implemented on the remote client device, acamera position associated with a 3D model viewer implemented on theremote client device, etc.). In one example, the user position can berepresented by three floating point numbers for the X, Y, and Zcoordinates of the user position in 3D space. In another example, data(e.g., a quaternion) representing orientation (e.g., a viewingdirection) of a virtual camera or a view frustum associated with aposition of a user in a 3D model rendered on the remote client device isreported to the server in addition to the user position. For example, aquaternion can comprise standard representations as four floating pointnumbers satisfying a particular relation, and can be reduced to threeindependent floating point numbers. In an aspect, the client reports anupdated user position to the server. For example, the remote clientdevice can report an updated position of a user in a rendering of a 3Dmodel (e.g., an updated viewing position associated with a viewerimplemented on the remote client device). In one example, the updateduser position can correspond to the initial user position. In anotherexample, the updated user position can be different than the initialuser position.

At 908, the server determines whether any data chunks remain to send tothe client. For example, the server can determine whether there are anyremaining data chunks at any level of detail which can be sent to theremote client device. If no, methodology 900 proceeds to 914. At 914,mesh loading is complete. If yes, methodology 900 proceeds to 910. At910, the server decides which data chunk to send to the client next. Forexample, if there are remaining data chunks then the server candetermine which data chunk and/or which level of detail to send to theclient next. In one example, the server can determine which data chunkand/or which level of detail to send to the client next based onposition data and/or orientation data determined at 906. At 912, theserver sends a next data chunk to the client. Next, at 906, the clientreports a new user position to the server. In one example, the new userposition can be the same as the previously reported user position. Inanother example, the new user position can be different than thepreviously reported user position. As such, methodology 900 can continueuntil the client no longer requires the mesh or until the server hasdetermined that the mesh loading is complete (e.g., at 914). In analternate embodiment, 908 and/or 910 can be implemented on the client.In an aspect, the server can transmit information associated with eachdata chunk and/or information associated with each level of detail for adata chunk to the client to facilitate determining whether any datachunks remain to send to the client and/or deciding which data chunk tosend to the client next.

In order to provide a context for the various aspects of the disclosedsubject matter, FIGS. 10 and 11 as well as the following discussion areintended to provide a brief, general description of a suitableenvironment in which the various aspects of the disclosed subject mattermay be implemented.

With reference to FIG. 10, a suitable environment 1000 for implementingvarious aspects of this disclosure includes a computer 1012. Thecomputer 1012 includes a processing unit 1014, a system memory 1016, anda system bus 1018. The system bus 1018 couples system componentsincluding, but not limited to, the system memory 1016 to the processingunit 1014. The processing unit 1014 can be any of various availableprocessors. Dual microprocessors and other multiprocessor architecturesalso can be employed as the processing unit 1014.

The system bus 1018 can be any of several types of bus structure(s)including the memory bus or memory controller, a peripheral bus orexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MSA), Extended ISA(EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB),Peripheral Component Interconnect (PCI), Card Bus, Universal Serial Bus(USB), Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1394), and SmallComputer Systems Interface (SCSI).

The system memory 1016 includes volatile memory 1020 and nonvolatilememory 1022. The basic input/output system (BIOS), containing the basicroutines to transfer information between elements within the computer1012, such as during start-up, is stored in nonvolatile memory 1022. Byway of illustration, and not limitation, nonvolatile memory 1022 caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable programmable ROM(EEPROM), flash memory, or nonvolatile random access memory (RAM) (e.g.,ferroelectric RAM (FeRAM). Volatile memory 1020 includes random accessmemory (RAM), which acts as external cache memory. By way ofillustration and not limitation, RAM is available in many forms such asstatic RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), doubledata rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM(SLDRAM), direct Rambus RAM (DRRAM), direct Rambus dynamic RAM (DRDRAM),and Rambus dynamic RAM.

Computer 1012 also includes removable/non-removable,volatile/nonvolatile computer storage media. FIG. 10 illustrates, forexample, a disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, Jaz drive, Zip drive, LS-100 drive, flash memory card, or memorystick. The disk storage 1024 also can include storage media separatelyor in combination with other storage media including, but not limitedto, an optical disk drive such as a compact disk ROM device (CD-ROM), CDrecordable drive (CD-R Drive), CD rewritable drive (CD-RW Drive) or adigital versatile disk ROM drive (DVD-ROM). To facilitate connection ofthe disk storage devices 1024 to the system bus 1018, a removable ornon-removable interface is typically used, such as interface 1026.

FIG. 10 also depicts software that acts as an intermediary between usersand the basic computer resources described in the suitable operatingenvironment 1000. Such software includes, for example, an operatingsystem 1028. Operating system 1028, which can be stored on disk storage1024, acts to control and allocate resources of the computer system1012. System applications 1030 take advantage of the management ofresources by operating system 1028 through program modules 1032 andprogram data 1034, e.g., stored either in system memory 1016 or on diskstorage 1024. It is to be appreciated that this disclosure can beimplemented with various operating systems or combinations of operatingsystems.

A user enters commands or information into the computer 1012 throughinput device(s) 1036. Input devices 1036 include, but are not limitedto, a pointing device such as a mouse, trackball, stylus, touch pad,keyboard, microphone, joystick, game pad, satellite dish, scanner, TVtuner card, digital camera, digital video camera, web camera, and thelike. These and other input devices connect to the processing unit 1014through the system bus 1018 via interface port(s) 1038. Interfaceport(s) 1038 include, for example, a serial port, a parallel port, agame port, and a universal serial bus (USB). Output device(s) 1040 usesome of the same type of ports as input device(s) 1036. Thus, forexample, a USB port may be used to provide input to computer 1012, andto output information from computer 1012 to an output device 1040.Output adapter 1042 is provided to illustrate that there are some outputdevices 1040 like monitors, speakers, and printers, among other outputdevices 1040, which require special adapters. The output adapters 1042include, by way of illustration and not limitation, video and soundcards that provide a means of connection between the output device 1040and the system bus 1018. It should be noted that other devices and/orsystems of devices provide both input and output capabilities such asremote computer(s) 1044.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. The remote computer(s) 1044 can be a personal computer, a server,a router, a network PC, a workstation, a microprocessor based appliance,a peer device or other common network node and the like, and typicallyincludes many or all of the elements described relative to computer1012. For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected via communication connection 1050. Networkinterface 1048 encompasses wire and/or wireless communication networkssuch as local-area networks (LAN), wide-area networks (WAN), cellularnetworks, etc. LAN technologies include Fiber Distributed Data Interface(FDDI), Copper Distributed Data Interface (CDDI), Ethernet, Token Ringand the like. WAN technologies include, but are not limited to,point-to-point links, circuit switching networks like IntegratedServices Digital Networks (ISDN) and variations thereon, packetswitching networks, and Digital Subscriber Lines (DSL).

Communication connection(s) 1050 refers to the hardware/softwareemployed to connect the network interface 1048 to the bus 1018. Whilecommunication connection 1050 is shown for illustrative clarity insidecomputer 1012, it can also be external to computer 1012. Thehardware/software necessary for connection to the network interface 1048includes, for exemplary purposes only, internal and externaltechnologies such as, modems including regular telephone grade modems,cable modems and DSL modems, ISDN adapters, and Ethernet cards.

It is to be appreciated that the computer 1012 can be used in connectionwith implementing one or more of the systems, components and/ormethodologies shown and described in connection with FIGS. 1-9. Inaccordance with various aspects and implementations, the computer 1012can be used to facilitate processing and/or transmitting 3D data. Incertain exemplary embodiments, the computer 1012 includes a component1006 (e.g., the processing component 102) that can contain, for example,a partitioning component, a data component, a selection component and/oran output component, each of which can respectively function as morefully disclosed herein.

FIG. 11 is a schematic block diagram of a sample-computing environment1100 with which the subject matter of this disclosure can interact. Thesystem 1100 includes one or more client(s) 1110. The client(s) 1110 canbe hardware and/or software (e.g., threads, processes, computingdevices). The system 1100 also includes one or more server(s) 1130.Thus, system 1100 can correspond to a two-tier client server model or amulti-tier model (e.g., client, middle tier server, data server),amongst other models. The server(s) 1130 can also be hardware and/orsoftware (e.g., threads, processes, computing devices). The servers 1130can house threads to perform transformations by employing thisdisclosure, for example. One possible communication between a client1110 and a server 1130 may be in the form of a data packet transmittedbetween two or more computer processes.

The system 1100 includes a communication framework 1150 that can beemployed to facilitate communications between the client(s) 1110 and theserver(s) 1130. The client(s) 1110 are operatively connected to one ormore client data store(s) 1120 that can be employed to store informationlocal to the client(s) 1110. Similarly, the server(s) 1130 areoperatively connected to one or more server data store(s) 1140 that canbe employed to store information local to the servers 1130.

It is to be noted that aspects or features of this disclosure can beexploited in substantially any wireless telecommunication or radiotechnology, e.g., Wi-Fi; Bluetooth; Worldwide Interoperability forMicrowave Access (WiMAX); Enhanced General Packet Radio Service(Enhanced GPRS); Third Generation Partnership Project (3GPP) Long TermEvolution (LTE); Third Generation Partnership Project 2 (3GPP2) UltraMobile Broadband (UMB); 3GPP Universal Mobile Telecommunication System(UMTS); High Speed Packet Access (HSPA); High Speed Downlink PacketAccess (HSDPA); High Speed Uplink Packet Access (HSUPA); GSM (GlobalSystem for Mobile Communications) EDGE (Enhanced Data Rates for GSMEvolution) Radio Access Network (GERAN); UMTS Terrestrial Radio AccessNetwork (UTRAN); LTE Advanced (LTE-A); etc. Additionally, some or all ofthe aspects described herein can be exploited in legacytelecommunication technologies, e.g., GSM. In addition, mobile as wellnon-mobile networks (e.g., the Internet, data service network such asinternet protocol television (IPTV), etc.) can exploit aspects orfeatures described herein.

While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthis disclosure also can or may be implemented in combination with otherprogram modules. Generally, program modules include routines, programs,components, data structures, etc. that perform particular tasks and/orimplement particular abstract data types. Moreover, those skilled in theart will appreciate that the inventive methods may be practiced withother computer system configurations, including single-processor ormultiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., PDA, phone), microprocessor-based or programmable consumer orindustrial electronics, and the like. The illustrated aspects may alsobe practiced in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network. However, some, if not all aspects of thisdisclosure can be practiced on stand-alone computers. In a distributedcomputing environment, program modules may be located in both local andremote memory storage devices.

As used in this application, the terms “component,” “system,”“platform,” “interface,” and the like, can refer to and/or can include acomputer-related entity or an entity related to an operational machinewith one or more specific functionalities. The entities disclosed hereincan be either hardware, a combination of hardware and software,software, or software in execution. For example, a component may be, butis not limited to being, a process running on a processor, a processor,an object, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components mayreside within a process and/or thread of execution and a component maybe localized on one computer and/or distributed between two or morecomputers.

In another example, respective components can execute from variouscomputer readable media having various data structures stored thereon.The components may communicate via local and/or remote processes such asin accordance with a signal having one or more data packets (e.g., datafrom one component interacting with another component in a local system,distributed system, and/or across a network such as the Internet withother systems via the signal). As another example, a component can be anapparatus with specific functionality provided by mechanical partsoperated by electric or electronic circuitry, which is operated by asoftware or firmware application executed by a processor. In such acase, the processor can be internal or external to the apparatus and canexecute at least a part of the software or firmware application. As yetanother example, a component can be an apparatus that provides specificfunctionality through electronic components without mechanical parts,wherein the electronic components can include a processor or other meansto execute software or firmware that confers at least in part thefunctionality of the electronic components. In an aspect, a componentcan emulate an electronic component via a virtual machine, e.g., withina cloud computing system.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

As used herein, the terms “example” and/or “exemplary” are utilized tomean serving as an example, instance, or illustration. For the avoidanceof doubt, the subject matter disclosed herein is not limited by suchexamples. In addition, any aspect or design described herein as an“example” and/or “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs, nor is it meantto preclude equivalent exemplary structures and techniques known tothose of ordinary skill in the art.

Various aspects or features described herein can be implemented as amethod, apparatus, system, or article of manufacture using standardprogramming or engineering techniques. In addition, various aspects orfeatures disclosed in this disclosure can be realized through programmodules that implement at least one or more of the methods disclosedherein, the program modules being stored in a memory and executed by atleast a processor. Other combinations of hardware and software orhardware and firmware can enable or implement aspects described herein,including a disclosed method(s). The term “article of manufacture” asused herein can encompass a computer program accessible from anycomputer-readable device, carrier, or storage media. For example,computer readable storage media can include but are not limited tomagnetic storage devices (e.g., hard disk, floppy disk, magnetic strips. . . ), optical discs (e.g., compact disc (CD), digital versatile disc(DVD), blu-ray disc (BD) . . . ), smart cards, and flash memory devices(e.g., card, stick, key drive . . . ), or the like.

As it is employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Further, processors can exploit nano-scalearchitectures such as, but not limited to, molecular and quantum-dotbased transistors, switches and gates, in order to optimize space usageor enhance performance of user equipment. A processor may also beimplemented as a combination of computing processing units.

In this disclosure, terms such as “store,” “storage,” “data store,” datastorage,” “database,” and substantially any other information storagecomponent relevant to operation and functionality of a component areutilized to refer to “memory components,” entities embodied in a“memory,” or components comprising a memory. It is to be appreciatedthat memory and/or memory components described herein can be eithervolatile memory or nonvolatile memory, or can include both volatile andnonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), flashmemory, or nonvolatile random access memory (RAM) (e.g., ferroelectricRAM (FeRAM). Volatile memory can include RAM, which can act as externalcache memory, for example. By way of illustration and not limitation,RAM is available in many forms such as synchronous RAM (SRAM), dynamicRAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), direct RambusRAM (DRRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM(RDRAM). Additionally, the disclosed memory components of systems ormethods herein are intended to include, without being limited toincluding, these and any other suitable types of memory.

It is to be appreciated and understood that components (e.g., processingcomponent, partitioning component, data component, selection component,output component, etc.), as described with regard to a particular systemor method, can include the same or similar functionality as respectivecomponents (e.g., respectively named components or similarly namedcomponents) as described with regard to other systems or methodsdisclosed herein.

What has been described above includes examples of systems and methodsthat provide advantages of this disclosure. It is, of course, notpossible to describe every conceivable combination of components ormethods for purposes of describing this disclosure, but one of ordinaryskill in the art may recognize that many further combinations andpermutations of this disclosure are possible. Furthermore, to the extentthat the terms “includes,” “has,” “possesses,” and the like are used inthe detailed description, claims, appendices and drawings such terms areintended to be inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

What is claimed is:
 1. A system, comprising: a memory storing computerexecutable components; and a processor configured to execute thefollowing computer executable components stored in the memory: apartitioning component that receives captured three-dimensional (3D)data associated with a 3D model of an interior environment andpartitions the captured 3D data into at least one data chunk; and anoutput component that transmits, to a remote device, first 3D data for adata chunk at a first level of detail and subsequently transmits, to theremote device, second 3D data for the data chunk at a second level ofdetail that is different than the first level of detail in response to adetermination that a viewpoint associated with a rendering of the 3Dmodel on the remote device satisfies a defined criterion.
 2. The systemof claim 1, wherein the output component transmits, to the remotedevice, the second 3D data for the at least one data chunk at the secondlevel of detail based on a position of the viewpoint associated with therendering of the 3D model on the remote device.
 3. The system of claim1, further comprising a selection component that selects the second 3Ddata in response to the determination that the viewpoint satisfies thedefined criterion.
 4. The system of claim 3, wherein the selectioncomponent is implemented on the remote device.
 5. The system of claim 3,wherein the selection component selects the second 3D data fortransmission, to the remote device, based on position data associatedwith the rendering of the 3D model on the remote device.
 6. The systemof claim 3, wherein the selection component selects the second 3D datafor transmission, to the remote device, based on a view frustumassociated with a rendering of the 3D model on the remote device.
 7. Thesystem of claim 3, wherein the selection component selects the second 3Ddata for transmission, to the remote device, based on a history ofposition data associated with a rendering of the 3D model on the remotedevice.
 8. The system of claim 3, wherein the selection componentselects the second 3D data for transmission, to the remote device, basedon a visibility-based culling technique.
 9. The system of claim 1,wherein the output component transmits, to the remote device, firsttexture data for the at least one data chunk at a first resolution andsubsequently transmits, to the remote device, second texture data forthe at least one data chunk at a second resolution in response to thedetermination that the viewpoint associated with the rendering of the 3Dmodel on the remote device satisfies the defined criterion.
 10. Thesystem of claim 1, wherein the output component transmits, to the remotedevice, first mesh data for the at least one data chunk at a firstresolution and subsequently transmits, to the remote device, second meshdata for the at least one data chunk at a second resolution in responseto the determination that the viewpoint associated with the rendering ofthe 3D model on the remote device satisfies the defined criterion. 11.The system of claim 1, wherein the partitioning component partitions thecaptured 3D data into the at least one data chunk based on anarchitectural element for the 3D model.
 12. A method, comprising:employing a processor that facilitates execution of computer executableinstructions stored on a non-transitory computer readable medium toimplement operations, comprising: partitioning capturedthree-dimensional (3D) data associated with a 3D model of an indoorenvironment into at least one data segment; transmitting, to a remotedevice at a first instance of time, first 3D data for the at least onedata segment at a first level of detail; and transmitting, to the remotedevice at a second instance of time subsequent to the first instance oftime, second 3D data for the at least one data segment at a second levelof detail that is different than the first level of detail in responseto a determination that a viewpoint position associated with a renderingof the 3D model on the remote device satisfies a defined criterion. 13.The method of claim 12, wherein the transmitting the second 3D datacomprises transmitting, to the remote device, the second 3D data for theat least one data segment at the second level of detail based onposition data for the viewpoint position associated with the renderingof the 3D model on the remote device.
 14. The method of claim 12,wherein the transmitting the second 3D data comprises transmitting, tothe remote device, the second 3D data for the at least one data segmentat the second level of detail based on a view frustum associated with arendering of the 3D model on the remote device.
 15. The method of claim12, further comprising: transmitting, to the remote device at the firstinstance of time, first texture data for the at least one data segmentat a first resolution; and transmitting, to the remote device at thesecond instance of time, second texture data for the at least one datasegment at a second resolution that is higher than the first resolutionin response to the determination that the viewpoint position associatedwith the rendering of the 3D model on the remote device satisfies thedefined criterion.
 16. The method of claim 12, further comprising:transmitting, to the remote device at the first instance of time, firstmesh data for the at least one data segment at a first resolution; andtransmitting, to the remote device at the second instance of time,second mesh data for the at least one data segment at a secondresolution that is higher than the first resolution in response to thedetermination that the viewpoint position associated with the renderingof the 3D model on the remote device satisfies the defined criterion.17. A hardware server, comprising: a memory storing computer executablecomponents; and a processor configured to execute the computerexecutable components to: partition three-dimensional (3D) dataassociated with a 3D model of an interior environment into at least onedata chunk associated with an architectural element for the 3D model,transmit, to a remote device at a first instance of time, first 3D datafor the at least one data chunk at a first level of detail, andtransmit, to the remote device at a second instance of time subsequentto the first instance of time, second 3D data for the at least one datachunk at a second level of detail that is different than the first levelof detail in response to a determination that a viewpoint associatedwith a rendering of the 3D model on the remote device satisfies adefined criterion.
 18. The hardware server of claim 17, wherein theprocessor is configured to transmit the second 3D data to the remotedevice based on a position of the viewpoint associated with therendering of the 3D model on the remote device.
 19. The hardware serverof claim 17, wherein the processor is further configured to execute thecomputer executable components to: transmit, to the remote device,texture data for the at least one data chunk.
 20. The hardware server ofclaim 17, wherein the processor is further configured to execute thecomputer executable components to: transmit, to the remote device,geometry data for the at least one data chunk.